GENERAL INFORMATION ------------------ This file provides documentation and context for the proposal-level metadata included in this dataset export. In the same directory as this file, you will find a JSON file named: metadata_.json which contains all the general metadata describing the proposal, such as where the measurements were taken, who participated, and which projects funded the work. We recommend opening the JSON file using a code or JSON editor for easier navigation and readability. 1. Dataset title: This information is found in the JSON file under the field: "title" 2. Authorship: Author information is divided into two parts: - The "pi" field contains the Principal Investigator's details, including "name", "surname", "email", "orcid" and "institutions" (each institution includes name, address, country, city, and website). - The "researchers" field is a list of other contributors using the same structure as "pi". DESCRIPTION ----------- 1. Dataset language: English 2. Abstract: Found under the "abstract" field. 3. Keywords: Particle Physics, Nuclear Physics, IABA-ICTS, CNA, CMAM, US, UAM. 4. Date of data collection: This is the submission date of the proposal dataset, found in "submission_date". 5. Publication date: [Not included. Could be provided separately or added to the JSON as "publication_date" if applicable.] 6. Grant information: Located under the `"projects"` field. For each project, the following metadata is available: - "title": Project title - "grant_number": Grant or project identifier - "agencies": List of funding agencies, each with "name", "alias", "ROR", "country", "region", and "website". 7. Geographical location of data collection: Inferred from the "institution" field and its "address", "city", and "country" properties. ACCESS INFORMATION ------------------ 1. Creative Commons License: CC-BY 2. Dataset DOI: [Not included. To be provided by the repository after upload.] 3. Related publication: [Not included. Could be added as a "related_publications" field.] 4. Link to related datasets: [Not included. Could be added in future versions.] VERSIONING AND PROVENANCE ------------------------- 1. Last modification date: [Not applicable.] 2. Were data derived from another source?: [Not applicable.] 3. Additional related data not included in this dataset: [Not applicable.] METHODOLOGICAL INFORMATION -------------------------- 1. Description of the methods used to collect and generate the data: [Included in the files metadata.] 2. Data processing methods: [Not applicable.] 3. Software or instruments needed to interpret the data: [Not applicable.] 4. Information about instruments, calibration and standards: [Not applicable.] 5. Environmental or experimental conditions: [Not applicable.] 6. Quality-assurance procedures performed on the data: [Not applicable.] FILE OVERVIEW ------------- 1. File naming convention: Each proposal metadata file is named as: metadata_.json where `` corresponds to the `"code"` field in the proposal JSON. 2. File list: - File name: `metadata_.json` Description: JSON file containing the general metadata for this proposal. - File name: `README_proposal.txt` Description: This README file providing documentation for the proposal metadata. 3. Relationship between files: This README provides documentation for the metadata JSON file located in the same directory. 4. File format: All metadata files are provided in .json format and are UTF-8 encoded. 5. Directory structure: The ZIP export is structured as follows: proposals_export.zip / files_export.zip └── / ├── metadata_.json ├── README_proposal.txt ├── _files/ │ ├── .json │ ├── .json │ └── ... │ └── README_files.txt ├── _files/ │ ├── .json │ └── ... │ └── README_cnastderdafiles.txt └── … SPECIFIC INFORMATION FOR TABULAR DATA ------------------------------------------- 1. Name file: _metadata.json 2. Number of rows and columns: This JSON file contains a hierarchical structure of nested objects and arrays. It is not tabular in the strict sense, but the top-level object contains 10 primary keys. 3. Variables list: [Each variable is described below. No units are used in this metadata file.] Variable name: "code" Description: Proposal identifier code. Units of measure or value labels: Text string (e.g., "CNA-TOFERDA002/25") Variable name: "title" Description: Title of the proposal or experiment. Units of measure or value labels: Text string Variable name: "abstract" Description: Brief description of the purpose or content of the proposal. Units of measure or value labels: Text string Variable name: "submission_date" Description: Date the proposal was submitted. Units of measure or value labels: Date string in ISO format (YYYY-MM-DD) Variable name: "institution" Description: Institution responsible for the measurements. Includes name, alias, address, country, city, and website. Units of measure or value labels: Structured object Variable name: "infrastructure" Description: Facility or instrument used for the experiment. Includes name and type. Units of measure or value labels: Structured object Variable name: "beamlines" Description: List of beamlines involved in the experiment. Each item includes code and name. Units of measure or value labels: List of objects Variable name: "techniques" Description: Techniques used in the experiment. Each item includes the full name and alias. Units of measure or value labels: List of objects Variable name: "pi" Description: Principal Investigator (PI) of the proposal. Includes name, surname, email, ORCID, and list of institutions. Each institution includes name, alias, address, country, city, and website. Units of measure or value labels: Structured object Variable name: "researchers" Description: List of additional researchers involved in the proposal. Each entry includes the same structure as the PI. Units of measure or value labels: List of structured objects Variable name: "projects" Description: Projects supporting the proposal. Each entry includes title, grant number, and funding insititutions. Each funding institution includes name, alias, address, country, city, and website. Units of measure or value labels: List of structured objects 4. Codes or symbols for missing data: [Not applicable.] 5. Special formats or abbreviations used: [Not applicable.] MORE INFORMATION ---------------- This metadata follows the structure defined in the FAIR principles. Please contact the data management team for more information or support. Inside each subdirectory named _files, you will find a file named README_.txt. This file provides documentation on both the experimental data files and the associated metadata JSON files for that specific file type. ------- Página de inicio: ProposalManagement Aquí aparecen listadas las propuestas disponibles según los permisos del usuario // src/pages/Proposals/ProposalManagement.js ------- Create Proposal:CreateProposalDialog Dialog con formulario de la propuesta mediante código en base externa o manual // src/pages/Proposals/CreateProposalDialog.js Usa modelos de select que recuperan la info de las tablas de la base de datos interna: InstitutionSelect from "./FileDialog/forms/common/InstitutionSelect"; InfrastructureSelect from "./FileDialog/forms/common/InfrastructureSelect"; BeamlineSelect from "./FileDialog/forms/common/BeamlineSelect"; TechniqueSelect from "./FileDialog/forms/common/TechniqueSelect"; PISelect from "./FileDialog/forms/common/PISelect"; Elección y diseño de principal Investigator (PI) y participantes CreatePiForm from "./FileDialog/CreatePiForm"; HumanPiResolution from "./FileDialog/HumanPiResolution"; ParticipantRow from "./FileDialog/ParticipantRow"; ----- Managmente Proposal: ProposalManagement // src/pages/Proposals/ProposalManagement.js Aquí están los botones de crear propuestas, buscarlas y muestra la tabla con las propuestas disponibles del usuario Tiene las funciones, handleCreated, loadProposals, handleExportSelected Y definir las columnas que tendrá la tabla, que mostrará y como: code, title, created_at, submission_date, institution, infrastructure, beamlines, techniques, pi, researchers, projects, actions Aqui modificamos como se verán los proyectos y researchers (projects_text y participants_text) ------ Detail Proposal: ProposalDetailPage // src/pages/Proposals/ProposalDetailPage.js Aqui se define como se muestran los detalles de cada propuesta. Al entrar aquí ves los metadatos generales, y científicos dependiendo de cada modelo de file. El como se muestran la tabla de resumen de los metadatos de cada muestra. En el DashboardLayout modificamos los metadatos generales que se muestran, condicionamos si source es manual se muestra project_text y participants_text si no se muestran los normales (project y researchers) ------ Export general metadata proposal: serilize_proposals en utils.py # iabaictsmetadata/utils.py Hay una función en el backend que define los datos que se exportarán en los json, que datos y como quedarán escritos, aquí puedo modificar los participants y projects.